feat(core): experimental in-progress steering hints (1 of 3)#19008
feat(core): experimental in-progress steering hints (1 of 3)#19008joshualitt merged 2 commits intomainfrom
Conversation
Summary of ChangesHello @joshualitt, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request introduces foundational elements for experimental in-progress steering hints, primarily by adding a robust UI testing framework ( Highlights
Changelog
Activity
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
The pull request introduces experimental steering hints using a lightweight model (gemini-2.5-flash-lite), infrastructure for in-process application testing (AppRig), and a refactor of core configuration initialization. A high-severity prompt injection vulnerability has been identified in flashLiteHelper.ts due to unsafe concatenation of user-provided steering hints into LLM prompts without proper escaping or sanitization, which is critical given the agent's access to powerful tools like shell execution. Implementing robust escaping for delimiters or using structured data formats for prompt construction is recommended to mitigate this risk. Additionally, several instances of string truncation logic violate the grapheme-aware rule for multi-byte Unicode characters.
b36f195 to
4239e8b
Compare
|
Size Change: +6.55 kB (+0.03%) Total Size: 24.5 MB
ℹ️ View Unchanged
|
c1a5fd3 to
3e0f67a
Compare
3e0f67a to
f333c82
Compare
f333c82 to
4a46c1f
Compare
Roll-up PR here:
#18973
This is a rebase / refactor of:
#18783
Part of a series to address issue #18782
This change lands a few supplementary pieces for testing as well as some utility functions